<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><table id="top_location_line" width="100%"><table id="top_location_line" width="100%"><tr width="100%"><td><a href="http://www.urchin.com"><img border="0" src="../images/google_sm.gif" width="135" height="41"></a></td><td width="100%"><span id="top_line" style="width: 100%; float: left; clear: both; border-bottom: 1px solid #CCC;"><span id="top_title" style="float: left; margin-top: 10px;"><b>Help Center</b></span></td></tr></table>
<div id="page" lang="en" dir="ltr">
<div dir="ltr" id="content" lang="en">
<p class="line867"><strong>Are there limitations to log file size?</strong> <p class="line874">Urchin's log processing engine can process webserver logs that are larger than  2GB, regardless of whether they are compressed with bzip (.bz2), gzip (.gz), or zip (.zip) since Urchin uncompresses the files using the zlib library. <p class="line874">However, Urchin's log processing engine uses the unzip/zip binaries in the util directory to create backups and archives of the reporting data for each profile. If the reporting data for a month is large enough to cause the zip file to exceed 2GB, Urchin will not be able to make backups or archives, and log processing will fail unless automatic backups and archives are disabled. In this case, you will need to manually back up the files with some other external utility. </div><div id="pagebottom"></div>
</div>


<div id="footer" style="clear: both; margin: 0; padding: 0; border-bottom:1px solid #CCC;"></div><div id="copyright" style="font-size: 70%; text-align: center;">&copy;2010 Google</div>
</body></html>